|
Author |
Thread Statistics | Show CCP posts - 3 post(s) |
Shin Chogan
|
Posted - 2008.10.24 15:47:00 -
[1]
Edited by: Shin Chogan on 24/10/2008 15:49:19
Originally by: CCP Casqade
Originally by: Anton Brienne
I think it may have something to do with running the client in a window; when I run full screen it doesn't crash before I can log on (which it normally does) but I haven't tried any serious playtesting, so I could be totally wrong.
Interesting. Are you running it using the window mode switch in the config file to start it up in window mode? If you are running it in full screen, do you eventually get the crash too?
I've come to the same conclusion as well. It is suspiciously coincidental with bringing another app to the foreground. I've not tried it full screen yet.
By the way using the window mode switch in the config file no longer works ... way to regression test your patches ;)
I've not run eve from the terminal yet - my crashes don't appear to be as frequent as some here, I can play for an uninterrupted hour or two (as long as I don't switch apps) But I've noticed a lot of error messages in the console logs that weren't there pre patch. I'll raise a bug report as you suggested but the short version is a lot of messages like the following : _NSAutoreleaseNoPool(): Object 0x3e5ab550 of class NSCFDictionary autoreleased with no pool in place - just leaking
Any chance you could release an UN Patch Patch ;)
|
Shin Chogan
|
Posted - 2008.10.24 16:36:00 -
[2]
Originally by: Ami Nia
Originally by: Shin Chogan By the way using the window mode switch in the config file no longer works ... way to regression test your patches ;)
It does work for me. Are you sure you did change the correct setting?
I was going to yes ... however doing a double check ... ooopps Wrong directory !!!!
<slaps self> Way to go shooting my mouth off :/
|
Shin Chogan
|
Posted - 2008.10.24 20:25:00 -
[3]
Originally by: Ami Nia
Originally by: Ami Nia
Originally by: Shin Chogan By the way using the window mode switch in the config file no longer works ... way to regression test your patches ;)
It does work for me. Are you sure you did change the correct setting?
Originally by: Shin Chogan _NSAutoreleaseNoPool(): Object 0x3e5ab550 of class NSCFDictionary autoreleased with no pool in place - just leaking
That means that cider did start a new thread that (directly or indirectly) uses Objective C data but forgot to setup a pool. It's a sign that something should be fixed and that some memory is probably being leaked, but it should not be too worrying and is probably unrelated to the crashes and instabilities.
It MAY have something to do with performance/instability that is noticeable after a long time playing, however. But it's easy to verify if that's the case: keep Activity Monitor up and check how much the application "eats" memory over time.
After monitoring the memory consumption and looking at the crash log I must say I'm nearly certain the "leak" is a non issue. It only happens at the very beginning, therefore no over-time-memory-leakage should be experienced.
Plus when EvE starts you see a process going up, then launching another process and finally dying out (look at the dock during startup). I'm 99% confident that it is the launcher process that has a thread that misses the Objective C memory pool initialization, therefore all the memory is actually reclaimed by the OS when that thread dies.
I've noticed these entries appearing when I dock as well. |
Shin Chogan
|
Posted - 2008.10.25 08:01:00 -
[4]
I tried starting and running in fullscreen last night, normally I play in a window, and despite many attempts to crash my client I couldn't - about 3 hours of uninterrupted play.
|
|
|
|